Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore: Document how to disallow remote state access #712

Closed
wants to merge 1 commit into from

Conversation

project-kmac
Copy link

From customer:

│ Error: could not create a remote state access configation: 400 Bad Request: /body must have required property 'allowedProjectIds', /body/accessibleFromEntireOrganization must be equal to constant, /body must match a schema in anyOf
seems silly, but the only way i found to disallow remote state access for env0 backend with terraform is to fill the allowed project id list with an string like "none":
resource "env0_environment_state_access" "disallow" {
accessible_from_entire_organization = false
allowed_project_ids = ["none"]
skipping allowed_project_ids or setting to [] yields the given error

@@ -42,7 +42,8 @@ resource "env0_environment_state_access" "example_entire_organization" {
### Optional

- `accessible_from_entire_organization` (Boolean) when this parameter is 'false', allowed_project_ids should be provided. Defaults to 'false'
- `allowed_project_ids` (List of String) list of allowed project_ids. Used when 'accessible_from_entire_organization' is 'false'
- `allowed_project_ids` (List of String) list of allowed project_ids. Used when 'accessible_from_entire_organization' is 'false'. To disallow remote state access for env0 backend, fill the allowed_project_id list with string "none". Skipping allowed_project_ids or setting to [] yields a 400 error. (e.g. ```accessible_from_entire_organization = false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TomerHeber TomerHeber closed this Sep 20, 2023
@TomerHeber
Copy link
Collaborator

TomerHeber commented Sep 20, 2023

will fix the issue instead.

#714

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants